Skip to content

Add workspace creation protocol. #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

outfoxxed
Copy link
Member

This protocol allows workspaces to be created outside of ext-workspace's create-by-name strategy.

Many compositors create workspaces dynamically based on content or focus. This attempts to encompass all common strategies I'm aware of, and leaves the door open for compositor specific workspace creation methods to use most of the protocol.

This is commonly used by bars and workspace switchers.

@outfoxxed outfoxxed mentioned this pull request May 23, 2025
@outfoxxed outfoxxed force-pushed the workspace-creation branch from c5f88f2 to 0706bb1 Compare June 16, 2025 11:32
@outfoxxed
Copy link
Member Author

addressed review

Copy link

@YaLTeR YaLTeR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

guess further feedback would need actually trying to impl this

@outfoxxed outfoxxed force-pushed the workspace-creation branch from dd96548 to 0b76622 Compare June 21, 2025 05:43
@outfoxxed
Copy link
Member Author

outfoxxed commented Jun 21, 2025

I've exposed capabilities at a workspace-group level, so applications can show UI elements based on the expected capabilities of a given group (e.g. insert button).

I could've done this either as an object you create from a workspace group, or an object that sends events for all workspace groups. I've chosen to do the second as it should be less of a pain to implement in clients, but I'm open to changing that.

Given further thought, this won't be very useful without considerably more data, and the most flexible solution that sets expectations properly is to just not do it. Not exposing anything makes client UI harder to handle but should also force clients not to make incorrect assumptions, and instead use targets to probe for capabilities where they plan to create a workspace.

@outfoxxed outfoxxed force-pushed the workspace-creation branch from 0b76622 to fc7609f Compare June 21, 2025 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants